Skip to content

Remove IAM user here.hfla - #218

Merged
ale210 merged 1 commit into
mainfrom
remove-iam-user-here-hfla
Oct 28, 2026
Merged

ale210 merged 1 commit into
mainfrom
remove-iam-user-here-hfla

Conversation

@ale210

@ale210 ale210 commented Oct 15, 2026

Copy link
Copy Markdown
Member

Part of #205 (step 1 of 2: remove here.hfla; a follow-up PR recreates the account as here, the GitHub handle)

What changes did you make?

  • Removed the iam_user_herehfla module block from terraform/aws-users.tf

Why did you make the changes (we will use this info to test)?

  • The account is being recreated under the GitHub handle here, as the naming convention expects (the block still carried its # Replace with GitHub handle placeholder)
  • Expected plan: 0 to add, 0 to change, 3 to destroy: the user, its login profile and its read-only-group membership
  • The live user has no access keys, MFA devices or attached policies, and its password was never used, so force_destroy has nothing extra to remove

@github-actions

github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Terraform plan in terraform
With backend config files: terraform/prod.backend.tfvars
With variables: iam_only = false

Plan: 0 to add, 0 to change, 3 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-   destroy

Terraform will perform the following actions:

  # module.iam_user_herehfla.aws_iam_user.user will be destroyed
  # (because aws_iam_user.user is not in configuration)
-   resource "aws_iam_user" "user" {
-       arn                  = "arn:aws:iam::035866691871:user/here.hfla" -> null
-       force_destroy        = true -> null
-       id                   = "here.hfla" -> null
-       name                 = "here.hfla" -> null
-       path                 = "/" -> null
-       tags                 = {
-           "Access Level" = "1"
-           "Project"      = "devops-security"
        } -> null
-       tags_all             = {
-           "Access Level" = "1"
-           "Project"      = "devops-security"
-           "managed-by"   = "terraform-devops-security"
        } -> null
-       unique_id            = "AIDAQQWOSJEPSJ2DCMAHY" -> null
#        (1 unchanged attribute hidden)
    }

  # module.iam_user_herehfla.aws_iam_user_group_membership.user_group_membership will be destroyed
  # (because aws_iam_user_group_membership.user_group_membership is not in configuration)
-   resource "aws_iam_user_group_membership" "user_group_membership" {
-       groups = [
-           "read-only-group",
        ] -> null
-       id     = "terraform-aJORSVMK4GqQzwO28JhNS81ud4" -> null
-       user   = "here.hfla" -> null
    }

  # module.iam_user_herehfla.aws_iam_user_login_profile.user_login will be destroyed
  # (because aws_iam_user_login_profile.user_login is not in configuration)
-   resource "aws_iam_user_login_profile" "user_login" {
-       id                      = "here.hfla" -> null
-       password                = (sensitive value) -> null
-       password_length         = 20 -> null
-       password_reset_required = true -> null
-       user                    = "here.hfla" -> null
    }

Plan: 0 to add, 0 to change, 3 to destroy.

✅ Plan applied in Apply Terraform changes on merge #54

@ale210
ale210 merged commit 1d9713d into main Oct 28, 2026
2 checks passed
@ale210
ale210 deleted the remove-iam-user-here-hfla branch October 28, 2026 19:22
@ale210 ale210 mentioned this pull request Oct 28, 2026
ale210 pushed a commit that referenced this pull request Oct 29, 2026
* Use S3 native state locking instead of DynamoDB (#218)

Replace the deprecated dynamodb_table backend parameter with
use_lockfile = true, drop the DynamoDB statement from the live
IncubatorTfPlanSecretsRead policy, and remove the lock-table setup
from CONTRIBUTING.md and the pre-work issue template.

The backend.tf comment makes the terraform-plan/apply workflows
trigger, since they only filter on **/*.tf.

* Clarify changes migrating lockfiles to s3 from dynamodb

Continues #218
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant